home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980901-19981211
/
000256_news@newsmaster….columbia.edu _Tue Nov 3 10:18:19 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA05222
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 3 Nov 1998 10:18:18 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA07164
for kermit.misc@watsun; Tue, 3 Nov 1998 10:18:18 -0500 (EST)
Path: news.columbia.edu!panix!news-peer.gip.net!news.gsl.net!gip.net!news.idt.net!news-a.ais.net!ais.net!news.minn.net!skypoint.com!not-for-mail
From: escargo@mirage.skypoint.com (David S Cargo)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: So, how's the GUI version coming?
Date: 3 Nov 1998 15:18:46 GMT
Organization: none
Lines: 28
Message-ID: <71n6sm$j59$1@shadow.skypoint.net>
References: <363daea0.0@news.ic.net> <71ku3i$7f9$1@apakabar.cc.columbia.edu> <71lctk$gtl$1@shadow.skypoint.net> <71ldoh$gmf$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: mirage.skypoint.com
Xref: news.columbia.edu comp.protocols.kermit.misc:9460
In article <71ldoh$gmf$1@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>Hi David.
And hi, back.
>Well, yes, we've considered a lot of things. At this point the GUI
>library isn't the issue -- it's the structure of C-Kermit itself,
>which until now has been a "modal" program. Before it can be GUI'd, it
>must be turned inside out, chopped up, and reassembled into a form that
>can (but need not be) event driven. Furthermore, every action that results
>from command parsing must be carefully isolated from the parsing itself.
>No automated tool can do this.
I didn't think that SWIG would automate the turning inside out, chopping,
and reassembling. I was addressing only the interfacing the resulting
pieces with a GUI. Knowing ahead of time that you would be interfacing
with Tcl and Tk would probably mean a different partitioning of the
resulting pieces than if you wouldn't.
One of the mixed differences would be that you could use tcl as the
scripting language. You could also use tcl to write an interpreter for
the existing scripting language for compatability.
Mainly, I was seeing Tk as a way for you to avoid the creation of yet
another graphics library.
David